home *** CD-ROM | disk | FTP | other *** search
- Path: news.york.ac.uk!jlo100
- From: jlo100@york.ac.uk (JL Orgill)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: ToolManager Problem
- Date: 19 Jan 1996 16:58:48 GMT
- Organization: The University of York, UK
- Message-ID: <4doik8$eoj@netty.york.ac.uk>
- References: <4dm238$nnf@netty.york.ac.uk>
- NNTP-Posting-Host: tower.york.ac.uk
- X-Newsreader: TIN [version 1.2 PL2]
-
- JL Orgill (jlo100@york.ac.uk) wrote:
- : Its a little strange this one. I start it from WBStartup, and if I just
- : have my main graphic dock (using icons) at the bottom, and all the rest
- : text, it works fine.
- : But in the secondry dock (text) which open sub-docks, I have one (Apps)
- : which has cute icons too. This also loads fine.
- : But there is another sub-dock (Prefs) which works fine in text mode. If I
- : assign only one graphic brush, it works fine (except for lots of blanked
- : buttons).
- : Heres the problem. If I try to assign icons to all of them (~29), then
- : machine crashes on bootup. It stops just after a grey rectangle has been
- : drawn where the main dock goes. Heres the really strange bit though. If I
- : remove TM from WBStartup, boot my machine, then start TM manually, it
- : works fine and dandy.
- : What the hell is going on? Is there a problem where TM hogs vital
- : resources or something? Help please?
-
- : Mistified
- : SteveB
-
- I had a real heavy play trying to get this licked last night. It's like
- TM is crashing if something else wants to use the hard drive or
- something. I have incidentally had the same type of crash when I selected
- use from the prefs, and quit Imagine3 that was running. So far the only
- reliable way I have of getting my system fully up and running (with lots
- of gfx in docks) is to start it after the loadwb cmd in startup-sequence.
- This has me seriously puzzled. Output from SnoopDos shows that it is
- happily accessing files mixed with other programs. Here's the most stupid
- bit though. 6 other WBSU progs + TM. I had a command to start SnoopDos at
- the start of user-startup, and output to a log file. If the snoopdos
- window is open, the system boot time is huge, but it boots OK. If the
- window is closed, the system is quicker, but it hangs. It all seems to be
- timing, but timing of what!!!!!!!!!!
-
- Heeeeeeeeeeeeeellllllllllllllllp!
- SteveB
-
-